Define an asset job per DIE data product#79
Merged
Conversation
Each product now has a named asset job ({product_id}_job) selecting its
full graph (sources → combine → geoserver), launchable on demand from
the Dagster UI. Schedules target these jobs instead of raw asset
selections, so scheduled runs and manual runs share one definition.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Your pull request is automatically being deployed to Dagster Cloud.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a named Dagster asset job for each DIE data product —
{product_id}_job— selecting that product's full graph (source assets → combine → geoserver). Schedules now target these jobs instead of raw asset selections.Why
Previously each product's schedule pointed at an ad-hoc
AssetSelection. There was no first-class, launchable unit for "materialize this product." With explicit jobs:Changes
orchestration/definitions.py:_product_selection(pid)— the per-product graph (geoserver leaf + everything upstream)._build_jobs()— onedefine_asset_jobper product, returned as{product_id: job}._build_schedules()now binds eachScheduleDefinitionto its job (job=).Definitions(jobs=...).Notes for reviewer
🤖 Generated with Claude Code